<?php
/**
 * <https://y.st./>
 * Copyright © 2016 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'title' => 'I&apos;ve documented the bulk of include.d',
	'body' => <<<END
<p>
	I started filling out job applications, but I quickly got distracted and started working on commenting my code instead.
	I also logged into the temp agency website and found that I&apos;ve been turned down for one job, one job is still pending, and consideration for the third job requires an interview and/or more paperwork.
	I wrote to the temp agency asking about how to set up the interview and/or get access to the paperwork.
</p>
<p>
	Seeing as I&apos;ve been unable to find any complete documentation of how to build templates for phpDocumentor, I decided that perhaps I should build my own parser for the syntax.
	My plan is to write up my comments, test them in the phpDocumentor, correct any errors generated, then actually generate the documentation in my own documentation generator.
	However, I&apos;ve run into a bit of stupidity in phpDocumentor.
	If the first thing in the file is the namespace declaration instead of a documentation comment, it throws an error.
	This is utter nonsense.
	I place my namespace declarations on the same line as the opening <code>&lt;?php</code> tag, and there shouldn&apos;t be a problem with that.
	The comments then begin on the second line.
	The namespace applies to the entire file, so in makes the most sense to include it with the opening <code>&lt;?php</code> tag as if it were an extension of it.
	For now, I&apos;ll move my namespace declarations to below the first comment section while checking the rest of the comments for errors, but I&apos;m not happy about it; it&apos;s ugly.
	I&apos;m not sure if I&apos;ll leave the namespace declaration there when I&apos;m done though.
	I might put it back where it belongs once I verify that that&apos;s the only &quot;error&quot; in each file&apos;s comments.
	On second thought, I&apos;ll continue to comply, but I&apos;ll write my disdain into the comments of every file in which I have to follow the stupid convention of commenting before namespacing.
	I&apos;ve gone through the list of <a href="https://manual.phpdoc.org./HTMLSmartyConverter/HandS/phpDocumentor/tutorial_tags.pkg.html">phpDocumentor</a> tags and written up a new template for files written for include.d.
	I&apos;ve also written up most of the documentation comments for function and constant files and some of the documentation for class files.
	I&apos;ve looked through the revision history to find the appropriate value for the @since tag in everything but class subcomponents; I&apos;ll look into the time that each of those was added as I document each class.
</p>
<p>
	My plan was to get back to job applications in the evening, but I ended up out collecting bullet shells with Vanessa, Cyrus, and our mother due to miscommunication on Cyrus&apos; part.
	When we got home, it was too late to finish with the applications, so I got back to work on documenting my code.
</p>
END
);
